Skip to content

RHDHBUGS-2260: trust corporate-issued certificate#2211

Open
deerskindoll wants to merge 14 commits into
redhat-developer:mainfrom
deerskindoll:RHDHBUGS-2260
Open

RHDHBUGS-2260: trust corporate-issued certificate#2211
deerskindoll wants to merge 14 commits into
redhat-developer:mainfrom
deerskindoll:RHDHBUGS-2260

Conversation

@deerskindoll
Copy link
Copy Markdown
Member

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s):

main, release-1.10
Issue:

https://redhat.atlassian.net/browse/RHDHBUGS-2260
Preview:

@rhdh-bot
Copy link
Copy Markdown
Collaborator

rhdh-bot commented May 18, 2026

PR Build Results

Build failed -- 32/34 titles | 72s
Preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-2211/ (stale -- title build failed, showing previous version)

control-access_authentication-in-rhdh

Error: /docs/titles/control-access_authentication-in-rhdh/build/en-US/master.xml fails to validate
Cause: Document structure validation failed
Fix: Run 'ccutil compile' locally and check the full error output

get-started_setting-up-and-configuring-your-first-red-hat-developer-hub-instance

Error: /docs/titles/get-started_setting-up-and-configuring-your-first-red-hat-developer-hub-instance/build/en-US/master.xml fails to validate
Cause: Document structure validation failed
Fix: Run 'ccutil compile' locally and check the full error output

View full logs


Content Quality Assessment

CQA Report

  • CQA-00a: Orphaned modules
  • CQA-00b: Directory structure
  • CQA-01: Vale AsciiDoc DITA compliance
  • CQA-02: Verify assembly structure
  • CQA-03: Verify content type metadata
  • CQA-04: Verify module templates
  • CQA-05: Verify required modular elements
  • CQA-06: Verify assemblies follow official template (one user story)
  • CQA-07: Verify TOC depth (max 3 levels)
  • CQA-08: Verify short description content quality
  • CQA-09: Verify short description format
  • CQA-10: Verify titles are brief, complete, and descriptive
  • CQA-11: Verify procedure prerequisites
  • CQA-12: Verify grammar and style (Vale)
  • CQA-13: Verify content matches declared type
  • CQA-14: Verify no broken links
  • CQA-15: Check redirects
  • CQA-16: Verify official product names
  • CQA-17: Verify legal disclaimers for preview features

Summary

Checks: 19 total, 19 pass, 0 fail

19 checks: 19 pass, 0 fail

Run node build/scripts/cqa/index.js --all --fix locally to review and auto-fix issues.


Updated 2026-05-20 15:14:23 UTC

@deerskindoll deerskindoll changed the title [DRAFT] RHDHBUGS-2260: trust CA-issued certificate [DRAFT] RHDHBUGS-2260: trust corporate-issued certificate May 18, 2026
Comment thread modules/RHDHBUGS-2260.adoc Outdated
====

.Prerequisites
* You have a CA-issued certificate.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather say You have access to the public root or intermediate certificate of the CA you wish to trust., as CA-issued certificate implies that you want to use a leaf certificate, not the CA.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Comment thread modules/RHDHBUGS-2260.adoc Outdated



If you want to inject multiple CAs or certificates chains, you have to:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather merge this in the step 2 for clarity.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done. I added it to the admonition to make sure it pops (visually)



.Procedure
. Export the certificate from its source.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather say: Export the corporate CA certificate chain (root and intermediate certificates) from its source.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done


.Procedure
. Export the certificate from its source.
. Convert the certificate to `.pem` format.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better to mention: Convert the certificate or the entire certificate chain to .pem format.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

====
. Create a secret containing the CA.
. Mount the secret into {product-very-short} environment. Follow the steps specific for your deployment method: Helm or Orchestrator.
. Set the `NODE_EXTRA_CA_CERTS` to point to the mount path of the secret.
Copy link
Copy Markdown
Member

@albarbaro albarbaro May 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would be more explicit on how to set the env variable, as you did for the secret.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Configmap? I'm sorry, I'm not sure what you mean. I didn't mention configmap anywhere (I think)?

Comment thread modules/RHDHBUGS-2260.adoc Outdated
Setting the CA directly as an environmental value is not supported.
====
//Add link!!!!!
. OPTIONAL: Set up {rhbk} metrics.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think metrics play any role here, this step can be omitted.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was a silly goose and mixed up where to mention the metrics. it's not supposed to be here, exactly as you said

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed. I featured it by mistake

@deerskindoll deerskindoll changed the title [DRAFT] RHDHBUGS-2260: trust corporate-issued certificate RHDHBUGS-2260: trust corporate-issued certificate May 20, 2026
@sonarqubecloud
Copy link
Copy Markdown

@deerskindoll deerskindoll added the Technical review needed 🔩 Test all the procedures label May 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Technical review needed 🔩 Test all the procedures

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants